Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference: 476-tree-1
name: 1662
tree-preservation-order: undefined
476-tpo-1
uprn
address-text
point: POINT (-1.023755 50.882418)
geometry: MULTIPOLYGON (((-1.023684 50.882411,-1.023687 50.882425,-1.023697 50.882437,-1.023712 50.882447,-1.023732 50.882454,-1.023754 50.882456,-1.023776 50.882454,-1.023796 50.882448,-1.023812 50.882438,-1.023822 50.882426,-1.023826 50.882412,-1.023823 50.882398,-1.023813 50.882386,-1.023797 50.882375,-1.023778 50.882369,-1.023756 50.882366,-1.023734 50.882369,-1.023714 50.882375,-1.023698 50.882385,-1.023688 50.882397,-1.023684 50.882411)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL